Skip to content

Thread custom process groups through MoE grad finalization#4782

Merged
yashaswikarnati merged 5 commits into
NVIDIA:mainfrom
yashaswikarnati:ykarnati/upstream-moe-custom-process-groups
May 18, 2026
Merged

Thread custom process groups through MoE grad finalization#4782
yashaswikarnati merged 5 commits into
NVIDIA:mainfrom
yashaswikarnati:ykarnati/upstream-moe-custom-process-groups

Conversation

@yashaswikarnati

Copy link
Copy Markdown
Contributor

What does this PR do ?

⚠️ For major changes (either in lines of code or in its impact), please make sure to first share a design doc with the team. If you're unsure what's the best way to do so, contact the @mcore-oncall.

Issue tracking

For PRs from open-source community contributors:

  • New features: a linked issue is required. Please open a feature request and reference it here before submitting the PR.
  • Small updates (bug fixes, minor improvements): a linked issue is recommended and will accelerate the PR review process.

Linked issue:

Contribution process

Pre-checks

  • I have added relevant unit tests
  • I have added relevant functional tests
  • I have added proper typing to my code Typing guidelines
  • I have added relevant documentation
  • I have run the autoformatter.sh on my PR

Code review

Feel free to message or comment the @mcore-oncall to help accelerate your merge into main. The less complex your PR is, the faster it will be approved and merged!

All PRs start as draft. If you open a non-draft PR, it will be automatically converted to draft.

Step 1: Mark PR as "Ready for Review"

  1. When your PR is ready, click Ready for Review.
  2. An oncall reviewer is auto-assigned and expert reviewers are notified based on your changes.
    • Some PRs may jump straight to step 2. This is determined by .github/CODEOWNERS.

⚠️ Only mark as ready once merge-conflicts are resolved and the CI is passing.
Final Review might get declined if these requirements are not fulfilled.

Step 2: Final Review

For PRs that change megatron/core, once all expert reviewers have approved, the Final Review label is applied automatically and final reviewers are assigned.

For PRs outside megatron/core, this step is skipped.

Step 3: Approved

Once all required reviewers have approved, the Approved label is applied automatically.

Merge

Any member of mcore-engineers will be able to merge your PR.

For MRs into `dev` branch The proposed review process for `dev` branch is under active discussion.

MRs are mergable after one approval by either eharper@nvidia.com or zijiey@nvidia.com.

@yashaswikarnati yashaswikarnati requested review from a team as code owners May 13, 2026 16:08
@copy-pr-bot

copy-pr-bot Bot commented May 13, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@svcnvidia-nemo-ci svcnvidia-nemo-ci marked this pull request as draft May 13, 2026 16:08
@github-actions

Copy link
Copy Markdown
Contributor

This PR has been automatically converted to draft because all PRs must start as drafts.

When you are ready for review, click Ready for Review to begin the review process. This will:

  1. Add the oncall reviewer (optional reviewer)
  2. Add required review teams based on your changes

See the contribution guide for more details.

@yashaswikarnati yashaswikarnati marked this pull request as ready for review May 13, 2026 16:09
@svcnvidia-nemo-ci svcnvidia-nemo-ci requested a review from a team May 13, 2026 16:10
embd_group = pg_collection.embd
pos_emb_group = pg_collection.pos_embd
dp_cp_group = pg_collection.dp_cp
tp_dp_cp_group = pg_collection.tp_dp_cp if config.moe_router_enable_expert_bias else None

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why need condition to set None, should already be asserted above?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

addressed, thanks

@yashaswikarnati

Copy link
Copy Markdown
Contributor Author

/ok to test d09720f

@svcnvidia-nemo-ci svcnvidia-nemo-ci added the Approved All necessary approvals have been made label May 14, 2026
@yashaswikarnati yashaswikarnati requested a review from a team as a code owner May 14, 2026 01:49
@svcnvidia-nemo-ci svcnvidia-nemo-ci removed the Approved All necessary approvals have been made label May 14, 2026
@yashaswikarnati

Copy link
Copy Markdown
Contributor Author

/ok to test 50dc962

@svcnvidia-nemo-ci svcnvidia-nemo-ci added the Approved All necessary approvals have been made label May 18, 2026
@yashaswikarnati yashaswikarnati enabled auto-merge May 18, 2026 16:57
@yashaswikarnati yashaswikarnati added this pull request to the merge queue May 18, 2026
@svcnvidia-nemo-ci

Copy link
Copy Markdown

🔄 Merge queue validation started!

You can track the progress here: https://github.com/NVIDIA/Megatron-LM/actions/runs/26047921193

Merged via the queue into NVIDIA:main with commit aa786b7 May 18, 2026
77 of 79 checks passed
@yashaswikarnati yashaswikarnati deleted the ykarnati/upstream-moe-custom-process-groups branch May 18, 2026 18:18
janEbert pushed a commit to janEbert/Megatron-LM that referenced this pull request Jun 2, 2026
yhgalaxy pushed a commit to yhgalaxy/Megatron-LM that referenced this pull request Jun 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Approved All necessary approvals have been made complexity: low

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants